Navigation Device

ABSTRACT

A navigation device includes: a hands-free call unit that is connected to a mobile-phone handset and provides a hands-free call; an acquisition unit that acquires from the mobile-phone handset data related to a phone number stored in the mobile-phone handset; a display control unit that displays a screen based upon the data related to the phone number acquired by the acquisition unit; a storage unit in which the screen displayed by the display control unit when power is turned off is stored; and a redisplay control unit that calls and redisplays the screen stored in the storage unit when the power is turned on again after having been turned off.

TECHNICAL FIELD

The present invention relates to a navigation device to which amobile-phone handset is connected so as to enable a hands-free call.

BACKGROUND ART

There are countries and regions that legally prohibit a driver of avehicle from holding a mobile-phone handset to operate it or make aphone call while the vehicle is in motion. For this reason, hands-freecall devices for mobile-phone handset and navigation devices including ahands-free call function are commercially available, and it is knownthat those products are mounted on vehicles after being devised so as toencourage the driver to concentrate on driving (refer to PatentLiterature 1).

CITATION LIST Patent Literature

[PATENT LITERATURE 1] Japanese Laid-Open Patent Publication No.H11-168549

SUMMARY OF INVENTION Technical Problem

However, in order for the driver not to concentrate on operating thenavigation device and viewing the screen, most of commercially availablevehicle-mounted navigation devices with a hands-free call function areconfigured to limit a part of user operations and display functionswhile the vehicle is in motion. For this reason, where the navigationdevice requires a number of operations or hierarchy levels inhierarchical display before the user executes desired processing such asconfirmation of incoming and outgoing call history or the like, there isa problem that such upper limit value capping may cause the desiredprocessing to be disabled.

Solution to Problem

According to the first aspect of the present invention, a navigationdevice comprises: a hands-free call unit that is connected to amobile-phone handset and provides a hands-free call; an acquisition unitthat acquires from the mobile-phone handset data related to a phonenumber stored in the mobile-phone handset; a display control unit thatdisplays a screen based upon the data related to the phone numberacquired by the acquisition unit; a storage unit in which the screendisplayed by the display control unit when power is turned off isstored; and a redisplay control unit that calls and redisplays thescreen stored in the storage unit when the power is turned on againafter having been turned off.

According to the second aspect of the present invention, in thenavigation device according to the first aspect, it is preferred that anincoming and outgoing call history related to a same phone numberacquired by the acquisition unit includes only a latest one history withrespect to each type of incoming answered calls, incoming missed calls,and outgoing calls.

According to the third aspect of the present invention, in thenavigation device according to the first or the second aspect, it ispreferred that the navigation device further comprises: a name inputunit that inputs a name of the data related to the phone number; and aname record unit that records individual identifying information of themobile-phone handset and the name having been input by the name inputunit while being associated with each other.

According to the fourth aspect of the present invention, in thenavigation device according to the third aspect, it is preferred thatthe navigation device further comprises: a search unit that searchesdata related to a phone number based upon the individual identifyinginformation; and an update unit that updates the data related to thephone number having been searched by the search unit to the data relatedto the phone number having been acquired by the acquisition unit.

According to the fifth aspect of the present invention, in thenavigation device according to the fourth aspect, it is preferred thatwhen the acquisition unit newly acquires latest data of the data relatedto the phone number, the search unit searches, based upon the individualidentifying information, for the data related to the phone number havingbeen acquired in a past by the acquisition unit, and the update unitupdates the data related to the phone number having been searched by thesearch unit to the latest data.

ADVANTAGEOUS EFFECT OF THE INVENTION

According to the present invention, at the time of hands-free callingusing the navigation device, the number of operations or the number ofhierarchy levels in hierarchical display before the user executesdesired processing can be reduced, thereby improving convenience.

BRIEF DESCRIPTION OF THE DRAWINGS

[FIG 1] A diagram showing the structure of the inside of avehicle-mounted navigation device and its periphery.

[FIG 2] A diagram showing the mechanism of management of phone numberdata stored in an auxiliary storage.

[FIG 3] An illustration showing a screen displaying incoming callhistory data of phone number data in the vehicle-mounted navigationdevice.

[FIG 4] An illustration showing an incoming and outgoing callintegration history display screen integrally displaying inchronological order incoming call history data and outgoing call historydata of phone number data in the vehicle-mounted navigation device.

[FIG 5] An illustration showing a missed call notification screen in thevehicle-mounted navigation device.

[FIG 6] A flowchart explaining a registration or update processingprocedure of phone number data in the vehicle-mounted navigation device.

[FIG 7] A flowchart explaining a specific processing procedure to becarried out in “normal use”, which is subroutine processing included inthe registration or update processing procedure of phone number data inthe vehicle-mounted navigation device.

DESCRIPTION OF EMBODIMENTS

An embodiment in which the present invention, which enables the numberof operations at the time of hands-free call to be reduced, is appliedto a vehicle-mounted navigation device will now be explained withreference to FIG. 1 to FIG. 7. FIG. 1 is diagram showing the structureof the inside of a vehicle-mounted navigation device 100 of the presentembodiment and its periphery.

A CPU 110 is an arithmetic processing unit that controls the wholevehicle-mounted navigation device 100, and the CPU 110 and itsperipheral circuits are connected with each other via a bus. Signals areinput to the CPU 110 from a current location detection sensor 121, anignition sensor 122, and a user input device 130. The peripheralcircuits are configured to include a main memory 115, an auxiliarystorage 140, a broadcasting tuner 150, a display module 160, ahands-free call control unit 170, a communication interface 180, and anaudio module 190. The main memory 115 is used as a work memory which isa work area of the CPU 110 and as a program memory in which a controlprogram is stored.

The current location detection sensor 121, being configured to include aGPS sensor, detects current location of a vehicle on which thevehicle-mounted navigation device 100 is mounted. The ignition sensor122 detects ON/OFF of the ignition of the vehicle. A vehicle speedsensor 123 detects the vehicle speed of the vehicle. The user inputdevice 130 is, for example, a touch screen, a push-button switch aroundthe periphery of the screen, a remote controller, a joystick, or astylus pen.

The auxiliary storage 140 stores therein road map data and POI (Point OfInterest, e.g., tourist spots and various facilities) information to beused for navigation processing. The auxiliary storage 140 also storestherein phone number data 200 (described later in the explanation ofFIG. 2). While the auxiliary storage 140 is, for instance, a hard diskdrive, it may be a CD, a DVD, a flash memory, or another recordingmedium, and its readout device.

The tuner 150 is used to receive data from a road traffic informationdistribution center, e.g., VICS Center (Japanese Registered Trademark)of Japan, via an antenna.

The display module 160 displays on its screen image data constituted toinclude text and/or graphics output from the CPU 110.

The hands-free call control unit 170 controls an operation of amobile-phone handset 300 and a hands-free call which is a call using themobile-phone handset 300 performed via the vehicle-mounted navigationdevice 100.

The communication interface 180 is used to perform data communicationbetween the vehicle-mounted navigation device 100 and the mobile-phonehandset 300. The data communication method may be wireless communicationsuch as Bluetooth (Japanese Registered Trademark) or infraredcommunication, or wired communication via cable connection. If Bluetoothis used, for example, the communication interface 180 is configured toinclude an RF (Radio Frequency) circuit for data transmission andreception (not shown in the figures).

The audio controller 190 performs control to convert voice that the useremitted to a microphone 191 into an audio signal and control to outputan audio signal to a speaker 192.

Next, phone number data stored in the auxiliary storage 140 will beexplained with reference to FIG. 2. The phone number data 200, which isto be read and set or updated in the hands-free call according to thepresent embodiment, is managed by providing each piece of the phonenumber data of a plurality of registered mobile-phone handsets with aregistration name. The registration name of the phone number data 200 ismanaged in association with the mobile-phone handset individualidentifying information 210. As a registration name, for instance, aBluetooth Device Name, which is defined by the Bluetooth standard, orany name (e.g., “Yamada (private use)”) according to a user input isused. As the mobile-phone handset individual identifying information210, for example, a Bluetooth Device Address, which is defined by theBluetooth standard, or a phone number is used.

FIG. 2 presents a situation where the phone number data 200 of fivemobile-phone handsets are read in the vehicle-mounted navigation device100 via wireless communication using Bluetooth, for instance, andmanaged in association with the mobile-phone handset individualidentifying information 210 #1 to #5, respectively. The phone numberdata 200 include speed dial data 251, phone book data 252, and incomingand outgoing call history data 253, for example. In FIG. 2, theregistration name of the phone number data #1 associated with themobile-phone handset #1 is “Yamada (private use)”. The registration nameof the phone number data #2 associated with the mobile-phone handset #2is “Yamada (business use)”. The registration name of the phone numberdata #3 associated with the mobile-phone handset #3 is “Ryoko's mobile”.The registration name of the phone number data #4 associated with themobile-phone handset #4 is “Hiroshi”. The registration name of the phonenumber data #5 associated with the mobile-phone handset #5 is “Yuuchan”.

The incoming and outgoing call history data 253 includes incoming callhistory data and outgoing call history data which are not shown in thefigures. In incoming call history data stored in the mobile-phonehandset itself, usually, whether or not each of the incoming calls hasbeen answered is recorded. When the incoming call history data is readin the vehicle-mounted navigation device 100, as for incoming calls fromthe same phone number, the latest answer history and the latest missedcall history are extracted and saved as incoming call history data. Itis to be noted that a missed call refers to an unanswered incoming call.In addition, as for outgoing calls to the same phone number, only thelatest outgoing call history is saved as outgoing call history data.

Next, a screen to be displayed in a hands-free call according to thepresent embodiment will be explained with reference to FIGS. 3 to 5.FIG. 3 is an example of a screen on which incoming call history data ofthe phone number data #1 associated with the mobile-phone handset #1 inFIG. 2 is displayed. In this example, the history of the latest fiveincoming calls is displayed. Each of the incoming calls is displayedwith time and whether the call was answered or missed. As mentionedearlier, as for incoming calls from the same phone number, only thelatest answer history and only the latest missed call history are savedin the incoming call history data. Accordingly, if there is one or moremissed calls made prior to 31 Jan. 2008 (Thu) 21:07 from a mobile-phonehandset owned by a person corresponding to “Mr. A” which corresponds tothe latest missed call history, any of the missed calls is notdisplayed. For example, even if five or more consecutive missed callsare made from the mobile-phone handset owned by a person correspondingto “Mr. A”, only the missed call history from the same phone number isdisplayed on the latest incoming call history screen as shown in FIG. 3.Thus, there is no need to perform an additional operation such asscrolling the screen for referring to an incoming call history fromanother phone number. However, an incoming call made at 14:52 of thesame day from the mobile-phone handset owned by a person correspondingto the “Mr. A” was answered, and hence the fact that the incoming callwas answered is displayed on the incoming call history screen.

FIG. 4 is an example of an incoming and outgoing call integrationhistory display screen on which incoming call history data and outgoingcall history data that constitute the incoming and outgoing call historydata 253 of the phone number data #1 associated with the mobile-phonehandset #1 in FIG. 2 are integrally displayed in chronological order.Each of the incoming calls or the outgoing calls is displayed with timeand whether the call was answered, missed, or outgoing. As mentionedearlier, as for incoming calls from the same phone number, only thelatest answer history and only the latest missed call history are savedin the incoming call history data, and as for outgoing calls to thephone number, only the latest outgoing call history is saved as theoutgoing call history data. Hence, even if there are a plurality ofanswered calls and a plurality of missed calls from the mobile-phonehandset owned by a person corresponding to “Mr. A”, histories other thanthe latest history of each of them are not displayed. The incoming callhistory from a mobile-phone handset owned by a person corresponding to“Ms. B” and the outgoing call history to the mobile-phone handset ownedby a person corresponding to “Ms. B” are both displayed.

FIG. 5 shows a missed call notification screen to be displayed when theuser missed an incoming call. The missed call notification screen isdisplayed until a next event (for instance, an input operation by theuser or a new incoming call) occurs. If the event is ignition OFFdetected by the ignition sensor 122 and furthermore if the mobile-phonehandset detected by the vehicle-mounted navigation device 100 aftersubsequent ignition ON is the same as the mobile-phone handset connectedat the ignition OFF, the missed call notification screen is displayedagain. The above operation associated with such ignition OFF andsubsequent ignition ON, i.e., an operation of redisplay after ignitionON of a display screen at ignition OFF, is also performed for a screenother than the missed call notification screen. An example in which ascreen other than the missed call notification screen, displayedimmediately prior to ignition OFF event occurrence, is redisplayed willbe presented in the explanation of FIG. 7 described later.

The registration or update processing procedure of the phone number data200 controlled by the CPU 110, when the mobile-phone handset isconnected to the vehicle-mounted navigation device 100, will beexplained with reference to the flowchart of FIG. 6. In a step S610, thevehicle-mounted navigation device 100 detects a mobile-phone handset bythe hands-free call control unit 170. In a step S611, thevehicle-mounted navigation device 100 reads individual identifyinginformation of the mobile-phone handset, searches for the mobile-phonehandset individual identifying information 210 acquired in the past thatis stored in the auxiliary storage 140, and matches the read individualidentifying information with the searched mobile-phone handsetindividual identifying information so as to enable connectionauthentication. As described earlier, the phone number data 200 ismanaged corresponding to the mobile-phone handset individual identifyinginformation 210, and thus searching for the mobile-phone handsetindividual identifying information 210 is also searching for the phonenumber data 200.

When in a step S612, a negative decision is made on “authenticationOK?”, i.e., when a decision is made that the mobile-phone handsetindividual identifying information read by the vehicle-mountednavigation device 100 in the step S611 has not been registered, a menuas to whether or not to make a new registration is displayed on thescreen in a step S613, and the vehicle-mounted navigation device 100waits for an input by the user. If a new registration is made, in a stepS614, a decision is made as to whether or not the CPU 110 is inoperation limitation mode where a part of operations and displayfunctions are limited while the vehicle is in motion. If a negativedecision is made, the mobile-phone handset individual identifyinginformation is stored in a step S615. After that, in a step S616,various settings for new registration are performed based upon a userinput. The various settings for new registration include, for example,the place of a folder in which the phone number data 200 is stored inthe auxiliary storage 140, the registration name of the phone numberdata 200 (but limited to a case where any name based upon a user inputis used), and the phone number provided to the mobile-phone handset.Following that, in a step S617, speed dial number data is set based upona user input, and in a step S618 and in a step S619, phone book data andincoming and outgoing call history data are read and acquired from theconnected mobile-phone handset, so that they are stored in the auxiliarystorage 140. Upon completion of those processing, in a step S620, a “newregistration” completion notification message is displayed on thescreen, and then the normal use such as calling the phone number data200 and operating the mobile-phone handset is enabled. Since if apositive decision is made in the operation limitation mode decisionprocessing in the step S614, processing requiring a user input operationis not performed, the flow of control proceeds to the step S618.

If in the step S612, a positive decision is made on “authenticationOK?”, the mobile-phone handset is connected, and in a step S624, adecision is made as to whether or not a suspend flag was set at the timeof the last ignition OFF. This suspend flag setting is carried out in“normal use” subroutine processing, which will be described later in theexplanation of FIG. 7. If a negative decision is made in the step S624,a decision is made in a step S625 as to whether or not thevehicle-mounted navigation device 100 is in operation limitation mode.If a negative decision is made in the step S625, the speed dial numberdata is updated in a step S627 based upon a user input. At this time, itmay be arranged that if a predetermined period of time has elapsed in astate where no user input exists, the processing times out and the flowof control proceeds to the next step. In a step S628 and a step S629,the latest phone book data and incoming and outgoing call history dataare read and acquired from the connected mobile-phone handset. The phonenumber data 200 acquired in the past and stored in the auxiliary storage140, which was searched in the step S611, is updated with the acquiredlatest phone book data and the incoming and outgoing call history data.Upon completion of those processing, in a step S630, a “phone numberdata update” completion notification message is displayed on the screen.If a positive decision is made on the operation limitation mode decisionprocessing in the step S625, necessary processing based upon a userinput operation is not performed, and thus the flow of control proceedsto the step S628.

If a positive decision is made in the step S624, in a step S631 a screenhaving been already stored by display screen storage processingdescribed later in the explanation of FIG. 7 is called and displayed,and in a step S632 a suspend flag is cleared.

After any of the completion of processing in the step S620, the negativedecision making in the step S613, the completion of processing in thestep S630, and the completion of processing in the step S632, the flowof control proceeds to a step S640. In the step S640, the flow ofcontrol proceeds to subroutine processing “normal use” described laterin the explanation of FIG. 7. Upon completion of the subroutineprocessing, the processing procedure of the phone number data 200 withthe mobile-phone handset being connected to the vehicle-mountednavigation device 100 is terminated.

Next, a specific processing procedure carried out in subroutineprocessing “normal use” stated as the step S640 in FIG. 6 will beexplained with reference to the flowchart of FIG. 7. Once the presentsubroutine processing “normal use” is started, in a step S711 the CPU110 stores data of a display screen that is displayed at the time intothe main memory 115 or a cache memory not shown in the figures, and thenwaits for any event to occur.

In a step S712, if a decision is made that an event has occurred in theCPU 110, a decision is made as to the content of the event (step S713,S723, S733, S743, or S753) and processing is performed according to thecontent. If the event occurred in the step S712 is a mobile-phonehandset disconnection event by a user operation of the step S713, thepresent subroutine processing “normal use” is terminated. If the eventoccurred in the step S712 is an ignition OFF event of the step S723(based upon the input from the ignition sensor 122), a suspend flag isset in a step S724 and the present subroutine processing “normal use” isterminated. A suspend flag at the time of ignition OFF is set, and thenthe ignition becomes ON. If the fact that the mobile-phone handset hasbeen connected is detected upon the connection authentication by readingindividual identifying information (FIG. 6, the step S611 to the stepS612 “Y”), the suspend flag having been set is detected (FIG. 6, thestep S624 “Y”). When the suspend flag is detected, a screen that wasstored in the step S711 of FIG. 7 immediately prior to the ignition OFFis called and displayed (FIG. 6, the step S631).

If the event occurred in the step S712 of FIG. 7 is a mobile-phoneincoming and outgoing call event of the step S733 or a phone number dataedition event by a user input, the phone number data 200 is updated in asubsequent step S734. If the event occurred in the step S712 is avehicle motion/stop switch event based upon an input from the vehiclespeed sensor 123 of the step S743, operation limitation mode on/offswitch is performed in a subsequent step S744. This description definesthe operation limitation mode as a mode in which a part of operationsand display functions are limited while the vehicle is in motion inorder for the driver not to concentrate on operating the vehicle-mountednavigation device and viewing the screen. If the event occurred in thestep S712 is a call termination event, an incoming and outgoing callhistory individual display/integrated display switch event by a useroperation, or a hierarchy switch event of the screen display in the stepS753, a screen is displayed corresponding to each event.

After any of the completion of the processing in the step S734, thecompletion of the processing in the step S744, and the completion of theprocessing in the step S753, the flow of control returns to the stepS711 and the display screen is stored. For example, if the eventoccurred in the step S711 is an incoming call event to the mobile-phonehandset of the step S733 and if the user answered it, the flow ofcontrol returns to the step S711 and the data of the display screenduring the call is stored in the main memory 115 or the cache memory notshown in the figures. If the user missed the call and the incoming callevent is terminated, a missed call notification screen is displayed asshown in FIG. 5 and the data of the screen is stored in the main memory115 or the cache memory not shown in the figures. The process flow inand after the step S712 is repeated as explained earlier. For instance,if the user answers the incoming call event, a call is initiated, andupon termination of the call, the event occurring in the step S712 is acall termination event of the step S753. If the user missed the incomingcall event and the incoming call event is terminated, the missed callnotification screen shown in FIG. 5 described earlier is displayed andthe data of the screen is stored in the main memory 115 or the cachememory not shown in the figures. Following that, if the ignition OFFevent of step S723 occurs as an occurring event in the step S712, asuspend flag is set in the step S724, and the subroutine processing“normal use” of the FIG. 7 is terminated. After that, if the ignition isturned on and the connection of the mobile-phone handset is continued,the missed call notification screen shown in FIG. 5 described earlier iscalled and displayed.

The vehicle-mounted navigation device 100 according to the embodimentdescribed above achieves the following operations and advantageouseffects. (1) It is arranged that the phone number data 200 to be storedin the vehicle-mounted navigation device 100 such as the speed dialnumber data 251, the phone book data 252, and the incoming and outgoingcall history data 253 are managed for each mobile-phone handset andidentified corresponding to the mobile-phone handset individualidentifying information 210. Due to this, when the registeredmobile-phone handset 300 is connected to the vehicle-mounted navigationdevice 100, the phone number data 200 corresponding to the mobile-phonehandset is made available without requiring selection processing by auser operation, thereby reducing the number of operations by the user.It will never occur that the user edits another phone number datacorresponding to another registered mobile-phone handset, therebypreventing unauthorized access to phone number data.

(2) It is arranged that the phone book data 252 and the incoming andoutgoing call history data 253 are read from the mobile-phone handset300, which has been connected to the vehicle-mounted navigation device100 and authenticated, via data communication. Due to this, when theregistered mobile-phone handset 300 is connected to the vehicle-mountednavigation device 100, the latest phone book data and incoming andoutgoing call history data retained by the mobile-phone handset can beread.

(3) As for the incoming and outgoing call history data 253 stored in thevehicle-mounted navigation device 100, similarly to a commonmobile-phone handset, incoming call history data and outgoing callhistory data are managed separately. However, it is arranged that, as ascreen display type, an integrated display function via incoming andoutgoing call history integrated display is provided in addition toindividual display such as incoming call history display and outgoingcall history display. Due to this, the user is allowed to confirm thelatest incoming and outgoing call history at a glance, thereby reducingthe number of operations necessary in switching an incoming call historydisplay and an outgoing call history display.

(4) In the vehicle-mounted navigation device 100, a display screenimmediately prior to the ignition being turned off in a state where themobile-phone handset 300 is connected is stored corresponding to themobile-phone handset individual identifying information 210. It isarranged that after that, when the ignition is turned on and connectionof the mobile-phone handset is detected based upon the mobile-phonehandset individual identifying information 210, the stored displayscreen immediately prior to the ignition OFF is redisplayed. Due tothis, even in an engine shutoff for the idle reduction while the vehicleis stopped that is accompanied with frequent ignition OFF/ON switchingwhen the vehicle travels in an urban area, for example, the number ofoperations necessary to redisplay the screen.

(5) As for the incoming and outgoing call history data 253, it isarranged to extract the latest answer history and the latest missed callhistory for incoming calls from the same phone number and save thosehistories and to extract the latest outgoing call history for anoutgoing call to the same phone number and save that history. Thisreduces an amount of operation by the user scrolling the incoming andoutgoing call history display screen, whereas display of a plurality ofincoming and outgoing call histories related to the same phone numberhas conventionally required the user to operate scrolling so as to referto the latest incoming and outgoing call history display related toanother phone number. Hence, highly useful information display can bereferred to with a small number of operations.

Variations

While FIG. 1 and FIG. 2 only present an example of a use ofBluetooth-based wireless communication for connection of themobile-phone handset 300 to the vehicle-mounted navigation device 100,the connection may be via infrared wireless communication or via wiredcommunication through a cable.

While in the explanation of FIG. 2 described earlier, the incoming andoutgoing call history data 253 includes incoming call history data andoutgoing call history data not shown in the figures, it may includeanswer history data, missed call history data, and outgoing call historydata depending upon the model of the mobile-phone handset 300 to beconnected. When the vehicle-mounted navigation device 100 reads thoseanswer history data, missed call history data, and outgoing call historydata, as for incoming calls from the same phone number it may bearranged to extract the latest answer history and save the history asanswer history data and extract the latest missed call history and savethe history as missed call history data. In this case, it may bearranged that when the user refers to the incoming call history displayscreen or the incoming and outgoing call history integrated displayscreen, as for incoming call history from the same phone number, thevehicle-mounted navigation device 100 extracts the latest answer historyand the latest missed call history from among the incoming and outgoingcall history data 253 and integrally display those histories as anincoming call history on the screen. Alternatively, it may be arrangedto generate an answer history display screen and a missed call historydisplay screen so as to display each of those screens.

In the explanations of FIG. 3 and FIG. 4 described earlier, as for theincoming and outgoing call history data 253, when incoming and outgoingcall history data is read from the mobile-phone handset, the latestanswer history and the latest missed call history are extracted andsaved as for incoming calls from the same phone number. However, it maybe arranged that when the user refers to the incoming call historydisplay screen or the incoming and outgoing call history integrateddisplay screen, as for incoming calls from the same phone number, thevehicle-mounted navigation device 100 extracts the latest incoming callhistory from among the incoming and outgoing call history data 253regardless of answered calls and missed calls and displays the latestincoming call history on the screen. At that time, it may be arranged todisplay on the screen whether the latest incoming call history was of ananswered call or a missed call.

In the explanations of FIG. 3 and FIG. 4 described earlier, as for theincoming and outgoing call history data 253, when incoming and outgoingcall history data is read from the mobile-phone handset, the latestanswer history and the latest missed call history are extracted andsaved as for incoming calls from the same phone number and the latestoutgoing call history is extracted and saved as for outgoing calls tothe same phone number. However, it may be arranged that when the userrefers to the incoming and outgoing call history display screen afterthe vehicle-mounted navigation device 100 reads all data, thevehicle-mounted navigation device 100, from among the incoming andoutgoing call history data 253, extracts the latest answer history andthe latest missed call history as for incoming calls from the same phonenumber, extracts the latest outgoing call history as for outgoing callsto the same phone number, and displays the latest answer history and thelatest outgoing call history on the screen respectively. Alternatively,it may be arranged to display all the data on the screen withoutperforming the extraction processing.

In the explanation of FIG. 6 described earlier, the user is not allowedto select whether or not to read and set or update the speed dial numberdata 251, the phone book data 252, and the incoming and outgoing callhistory data 253. However, for instance, it is possible to arrange thatphone book data can be prevented from undergoing overwrite processingthat is not desired by the user. In other words, it may be arranged thatthe user is allowed to select whether or not to read and set or updateeach of the data.

In the explanation of FIG. 6 described earlier, reading and setting orupdating the speed dial number data 251, the phone book data 252, andthe incoming and outgoing call history data 253 cause data beforeundergoing overwrite processing to be lost. In such case, it isconsidered that restoration processing may be difficult or impossible ifthose data are overwritten by data including an unexpected error or dataincluding false information, for example. Thus, it may be arranged toretire and save backup data of each of the last data when each of thedata is read and set or updated. The backup data may be retired andsaved in the auxiliary storage 140 or an externally connected storagedevice such as a removable disk.

In the explanation of FIG. 7 described earlier, an ignition OFF eventfrom the ignition sensor 122 is to be detected in the step S723. Anignition OFF event is detected by inputting signals from the ignitionsensor 122 and a user input device 130 to the CPU 110. However, it maybe arranged that an external device that detected the ignition OFFevent, e.g., an engine control unit (ECU), notifies the CPU 110 ofignition OFF via inter-processor communication. At this time, the ECUmay not immediately stop power supply to the vehicle-mounted navigationdevice 100 but stop power supply after a predetermined period of timehas elapsed. Alternatively, it may be arranged that an ignition OFFstops power supply to the vehicle-mounted navigation device 100, thusleaving only auxiliary power supply to auxiliaries including thevehicle-mounted navigation device 100, so as to detect an ignition OFFevent. In addition, it may be arranged that an ignition OFF signal isinput directly from the ignition to the CPU 110 so as to detect anignition OFF event.

The above explanation presents an example in which the plurality ofmobile-phone handsets 300 are connected to the vehicle-mountednavigation device 100, and thus the mobile-phone handset individualidentifying information 210 is used. However, if only one mobile-phonehandset 300 is to be connected, the mobile-phone handset individualidentifying information 210 may not be used.

While the above explanation presents an embodiment in which the presentinvention, which can achieve reduction in the number of operations at ahands-free call, is applied to a vehicle-mounted navigation device, itmay be applied to a non-vehicle-mounted navigation device. For example,it may be applied to a PND (Personal Navigation Device) as long as aninput signal from the ignition sensor 122 can be detected.

The embodiment and the variations described above may be combined.

In addition, the present invention may be embodied in any way other thanthose described in reference to the embodiment and the variations, aslong as the functions characterizing the present invention remainintact.

The disclosure of the following priority application is hereinincorporated by reference:

Japanese Patent Application No. 2009-97294 (filed on Apr. 13, 2009)

1. A navigation device, comprising: a hands-free call unit that isconnected to a mobile-phone handset and provides a hands-free call; anacquisition unit that acquires from the mobile-phone handset datarelated to a phone number stored in the mobile-phone handset; a displaycontrol unit that displays a screen based upon the data related to thephone number acquired by the acquisition unit; a storage unit in whichthe screen displayed by the display control unit when power is turnedoff is stored; and a redisplay control unit that calls and redisplaysthe screen stored in the storage unit when the power is turned on againafter having been turned off.
 2. A navigation device according to claim1, wherein: an incoming and outgoing call history related to a samephone number acquired by the acquisition unit includes only a latest onehistory with respect to each type of incoming answered calls, incomingmissed calls, and outgoing calls.
 3. A navigation device according toclaim 1, further comprising: a name input unit that inputs a name of thedata related to the phone number; and a name record unit that recordsindividual identifying information of the mobile-phone handset and thename having been input by the name input unit while being associatedwith each other.
 4. A navigation device according to claim 3, furthercomprising: a search unit that searches data related to a phone numberbased upon the individual identifying information; and an update unitthat updates the data related to the phone number having been searchedby the search unit to the data related to the phone number having beenacquired by the acquisition unit.
 5. A navigation device according toclaim 4, wherein: when the acquisition unit newly acquires latest dataof the data related to the phone number, the search unit searches, basedupon the individual identifying information, for the data related to thephone number having been acquired in a past by the acquisition unit, andthe update unit updates the data related to the phone number having beensearched by the search unit to the latest data.